New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
template mappings are not loading in 0.90.8 #4511
Comments
Hey @seallison can you gimme more information what you mean by template mapping and maybe provide a small recreation gist for the problem you see? |
Hey, there were a couple of bugs fixed for 0.90.8 regarding file based mapping template loading - actually template loading by file was not working until 0.90.8 in a couple of previous 0.90 releases (wondering that this has worked for you so far). I am very happy to help and debug the issue with you, if you help with a bit more information. |
This is an example of what I'm talking about: https://gist.github.com/seallison/8031640 Let me know if you need any additional information. Thanks! |
@spinscale all of my mappings have been in templates that I construct like in my gist. I've deployed this using 0.90.0, 0.90.3, and 0.90.5 without issue. |
I can see why it happens. A quick fix is to remove the most outer data structure named
|
The fixes introduced in elastic#4235 and elastic#4411 do not take into account, that a template JSON in the config/ directory includes a template name, as opposed when calling the Put Template API. This PR allows to put both formats (either specifying a template name or not) into files. However you template name/id may not be one of the template element names like "template", "settings", "order" or "mapping". Closes elastic#4511
We gonna revert the revert to make sure people that were on |
The fixes introduced in #4235 and #4411 do not take into account, that a template JSON in the config/ directory includes a template name, as opposed when calling the Put Template API. This PR allows to put both formats (either specifying a template name or not) into files. However you template name/id may not be one of the template element names like "template", "settings", "order" or "mapping". Closes #4511
The fixes introduced in elastic#4235 and elastic#4411 do not take into account, that a template JSON in the config/ directory includes a template name, as opposed when calling the Put Template API. This PR allows to put both formats (either specifying a template name or not) into files. However you template name/id may not be one of the template element names like "template", "settings", "order" or "mapping". Closes elastic#4511
- Renamed IndexMetaData#removerAlias to removeAlias - Removed IndexTemplateMetaData#fromXContentStandalone unused method (relates to #4511) - MetaDataIndexAliasesService fix typo in comment - Alias removed unused constructor that accepts both alias name and filter
- Renamed IndexMetaData#removerAlias to removeAlias - Removed IndexTemplateMetaData#fromXContentStandalone unused method (relates to #4511) - MetaDataIndexAliasesService fix typo in comment - Alias removed unused constructor that accepts both alias name and filter
The fixes introduced in elastic#4235 and elastic#4411 do not take into account, that a template JSON in the config/ directory includes a template name, as opposed when calling the Put Template API. This PR allows to put both formats (either specifying a template name or not) into files. However you template name/id may not be one of the template element names like "template", "settings", "order" or "mapping". Closes elastic#4511
I have templates that define specific mappings. In testing 0.90.8 today, I noticed that the template mappings are not being used when I load data in to an index that matches the template. This has worked in all previous versions of ElasticSearch that I have used (0.19x -> 0.90.7).
The text was updated successfully, but these errors were encountered: